Methods systems and computer readable media for providing real time data network usage information using subscription profile repository (spr)

ABSTRACT

A method for providing real time data network usage information using an SPR includes receiving a request for real time data network usage information. The method further includes, in response to the request, effecting a data change for the subscriber in the SPR. The method further includes, at the SPR, in response to the data change, sending a notification of the change to a policy and changing rules function (PCRF). The method further includes, at the PCRF, in response to the notification of the data change, requesting real time data network usage information from at least one policy and charging enforcement function (PCEF) serving the subscriber. The method further includes, at the PCRF, receiving the data network usage information from the at least one serving PCEF. The method further includes providing an indication of the real time data network usage information to the SPR.

PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No.14/085,779, filed Nov. 20, 2013, the disclosure of which is incorporatedherein by reference in its entirety.

TECHNICAL FIELD

The subject matter described herein relates to providing real time datanetwork usage information to data network subscribers. Moreparticularly, the subject matter described herein relates to methods,systems, and computer readable media for providing real time datanetwork usage information using an SPR.

BACKGROUND

In data communications networks, it is desirable for data communicationsnetworks subscribers to be able to obtain, in real time, current datanetwork usage information. For example, if a data network subscribersubscribes to use five gigabytes of data per month, it may be desirablefor the subscriber to be able to obtain, in real time, the subscriber'scurrent data network usage, so that the subscriber can purchase datacapacity and/or change his or her data network usage behavior.

One approach for providing data network usage information may be to usea subscription profile repository (SPR). In long term evolution (LTE)networks, the SPR stores a subscriber's data network usage profile,i.e., the data allocation to which the subscriber subscribes and alsousage information. However, the usage information in SPR is typicallyonly updated when a data network session terminates. It may be desirablefor the subscriber to obtain data network usage information in real timewhile the subscriber is participating in one or more data networksessions. Waiting until session termination to obtain this informationmay not be desirable in some instances.

Another option for providing data network usage information to asubscriber may be to obtain the data network usage information from thepolicy control and enforcement function (PCEF). However, the PCEF thatserves a particular subscriber is determined dynamically. An informationtechnology (IT) system that a subscriber contacts to obtain networkusage information may not have current PCEF information for asubscriber. Thus, having an IT system obtain data network usageinformation directly from the PCEF may not be possible due to the lackof knowledge of the serving PCEF. It is also not desirable to retrievefast changing dynamic state data (such as current byte count of asession) using an IT interface.

Even if the PCEF could be queried by an IT system for a subscriber'sdata network usage information, the PCEF may not have a complete view ofthe subscriber's data network usage allocation. In this scenario, thePCRF is the usage manager, the PCEF is the usage tracker, and the SPR isthe long term storage of usage information. When a user session firstcomes up, the usage manager reads from storage the usage information andcalculates what's available for the session. For example, a subscriber'sthe monthly limit may be 5 GB and the subscriber has used 1 GB. So theusage manager (the PCRF) knows that 4 GB is available for the usersession. The PCRF may not allocate the entire amount to the usagetracker (the PCEF). The PCRF may allocate to the tracker 100 MB to betracked. When the subscriber uses up the amount, 100 MB, the trackerreports it to the manager, which may then allocate another 100 MB chunk.It may happen a few times during the life time of the session.Continuing the example here, the subscriber may be using the 4th 100 MBchunk. The usage manager is the only one that knows this −1.3 GB of themonthly allowance is used and the user is in the process of consuminganother 100 MB chunk. Even if the IT system is able to connect to thePCEF and retrieve the snapshot, the only thing the IT system canidentify is how much of the 100 MB chunk is used, e.g., 60M. On theother hand, the PCRF as the usage manager will perform necessarycalculations of the previous chunks consumed before writing the finalvalue to the SPR. Thus, contacting the PCEF alone may not provide acomplete picture of the subscriber's data network usage.

Yet another problem of obtaining usage information directly from a PCEFis that the user may have multiple concurrent sessions served bydifferent PCEFs. In such a case, if the IT system contacts a singlePCEF, the IT system will not have all of the subscriber's currentnetwork usage. For a direct interface to provide an accurate usagecount, the IT system would be required to have direct interfaces to anyPCEF that could possibly serve a subscriber. Such a solution is notscalable or practical.

Providing current data network usage information may be useful to asubscriber and a network operator. For example, if the current sessionwill cause the subscriber to exceed his data allocation, the subscribermay wish to have this information during the session so that thesubscriber can terminate the session or purchase additional data networkcapacity. The network operator may desire to offer the subscriber theopportunity to purchase additional data network usage quota before thecurrent quota is exceeded.

Accordingly, in light of these difficulties, there exists a need formethods, systems, and computer readable media for providing real timedata network usage information using an SPR.

SUMMARY

The subject matter described herein relates to methods, systems, andcomputer readable media for providing real time data network usageinformation using an SPR. One method includes receiving a request forreal time data network usage information. The method further includes,in response to the request, effecting a data change for the subscriberin the SPR. The method further includes, at the SPR, in response to thedata change, sending a notification of the change to a policy andchanging rules function (PCRF). The method further includes, at thePCRF, in response to the notification of the data change, requestingreal time data network usage information from at least one policy andcharging enforcement function (PCEF) serving the subscriber. The methodfurther includes, at the PCRF, receiving the data network usageinformation from the at least one serving PCEF. The method furtherincludes providing an indication of the real time data network usageinformation to the SPR.

As used herein, the term “real time data network usage information”refers to a snapshot of data network usage information that is currentat the time it was obtained. For example, a snapshot of real time datenetwork usage information may be the value of a network usage countermaintained by a PCEF at the time a request for such information isreceived by the PCEF and after the PCEF has had time to process therequest. It is understood that the data network usage information maychange at a rate of thousands of bytes per second. Thus, the real timedata network usage information obtained using the mechanisms describedherein may not be the exact current data network usage count by the timethe information is provided back to the subscriber. However, the term“real time data network usage information” is intended to include datanetwork usage information obtained at the request of a subscriber or anetwork operator that is more current than the data network usageinformation obtained at the time of the last session terminationinvolving the subscriber.

The subject matter described herein can be implemented in software incombination with hardware and/or firmware. For example, the subjectmatter described herein can be implemented in software executed by aprocessor. In one exemplary implementation, the subject matter describedherein can be implemented using a non-transitory computer readablemedium having stored thereon computer executable instructions that whenexecuted by the processor of a computer control the computer to performsteps. Exemplary computer readable media suitable for implementing thesubject matter described herein include non-transitory computer-readablemedia, such as disk memory devices, chip memory devices, programmablelogic devices, and application specific integrated circuits. Inaddition, a computer readable medium that implements the subject matterdescribed herein may be located on a single device or computing platformor may be distributed across multiple devices or computing platforms.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter described herein will now be explained with referenceto the accompanying drawings of which:

FIG. 1 is a network diagram illustrating a system for providing realtime data network usage information using an SPR according to anembodiment of the subject matter described herein;

FIG. 2 is a network diagram illustrating an exemplary message flow forproviding real time data network usage information using an SPRaccording to an embodiment of the subject matter described herein;

FIG. 3 is a block diagram illustrating exemplary components of an ITsystem for providing real time data network usage information using anSPR according to an embodiment of the subject matter described herein;

FIG. 4 is a block diagram illustrating exemplary components of an SPRfor providing real time data network usage information using the SPRaccording to an embodiment of the subject matter described herein;

FIG. 5 is a block diagram illustrating exemplary components of a PCRFfor providing real time data network usage information using an SPRaccording to an embodiment of the subject matter described herein;

FIG. 6 is a block diagram illustrating exemplary components of a PCEFfor providing real time data network usage information using an SPRaccording to an embodiment of the subject matter described herein;

FIG. 7 is a flow chart illustrating exemplary steps performed by an ITsystem in providing real time data network usage information using anSPR according to an embodiment of the subject matter described herein;

FIG. 8 is a flow chart illustrating exemplary steps performed by an SPRin providing real time data network usage information using the SPRaccording to an embodiment of the subject matter described herein;

FIG. 9 is a flow chart illustrating exemplary steps performed by a PCRFin providing real time data network usage information according to anembodiment of the subject matter described herein; and

FIG. 10 is a flow chart illustrating exemplary steps performed by a PCEFin providing real time data network usage information using an SPRaccording to an embodiment of the subject matter described herein.

DETAILED DESCRIPTION

The subject matter described herein includes methods, systems, andcomputer readable media for providing real time data network usageinformation using an SPR. FIG. 1 is a network diagram illustrating anexemplary network architecture in which the subject matter describedherein may operate. Referring to FIG. 1, a subscription profilerepository (SPR) 100 stores subscription information for data networksubscribers. SPR 100 may communicate with one or more policy andcharging rules functions (PCRFs) 102 to provide policy information fordata network subscribers to PCRFs 102. PCRFs 102 install policies forsubscribers on policy and charging enforcement functions (PCEFs) 104.PCEFs 104 maintain data network usage information for subscribers andenforce policies. When a subscriber, such as subscriber 106, desires toobtain real time data network usage information, the subscriber maycontact an information technology (IT) system 108 associated with thesubscriber's mobile operator or other data network service provider. Onepossible solution for providing the policy information to the subscriberis to have IT system 108 obtain the information from SPR 100. However,SPR 100 is not updated frequently enough to provide real time datanetwork usage information. Another possible solution is to have ITsystem 108 obtain the data network usage information directly from aPCEF 104. However, because the PCEF that serves a particular subscriberis dynamically assigned, IT system 108 may not have the visibility todirectly contact the PCEF serving the subscriber.

In light of these difficulties, a mechanism for triggering updating ofthe data network usage information maintained by SPR 100 is provided.FIG. 2 illustrates a method and system for providing real time datanetwork usage information regarding a subscriber according to anembodiment of the subject matter described herein. Referring to FIG. 2,in step 1, subscriber 106 requests data network usage information fromIT system 108. In step 2, IT system 108 sets a flag for the subscriberwith SPR 100. Setting a flag in the profile of the subscriber effects adata change in the subscriber's profile. Effecting a data change in thesubscriber's profile triggers an existing mechanism of the SPR to notifythe PCRF serving the subscriber of the data change. This mechanism isthe push notification request (PNR) message sent from SPR 100 to servingPCRF 102. The following illustrates exemplary fields that may beincluded in a push notification request message:

< Push-Notification-Request > ::=         < Diameter Header: 309, REQ,PXY, 16777217 >            < Session-Id >            {Vendor-Specific-Application-Id }            { Auth-Session-State }           { Origin-Host }            { Origin-Realm }            {Destination-Host }            { Destination-Realm }            *[Supported-Features ]            { User-Identity }            [Wildcarded-Public-Identity ]            [ Wildcarded-IMPU ]            [User-Name ]            { User-Data }            *[ AVP ]            *[Proxy-Info ]            *[ Route-Record ]The above illustrated format for the push notification request messageis specified by “3rd Generation Partnership Project; TechnicalSpecification Group Core Network and Terminals; Sh Interface Based onthe Diameter Protocol; Protocol Details,” TR 29.329 (Release 12) (2013),the disclosure of which is incorporated herein by reference in itsentirety. In the above illustrated message format, part of the user dataAVP may be used to communicate to PCRF 102 that the message is a requestfor updated data network usage information for the subscriber identifiedby the subscriber identification field.

The purpose of the PNR request is to notify a Diameter client by aDiameter server of changes in user data maintained by the server. Inthis instance, SPR 100 is serving as the Diameter server and PCRF 102 isserving as the Diameter client. It should be emphasized that SPR 100maintains current serving PCRF information for the subscriber and thusit is not necessary for IT system 108 to have direct access to servingPCRF information.

In response to receiving the PNR message, PCRF 102 recognizes the PNRmessage as a request for real time data network usage information andcontacts the PCEF serving the subscriber in step 4. PCRF 102 maintainsserving PCEF information for a subscriber because PCRF 102 is the nodethat installs policies on the PCEF for the subscriber.

PCEF 104 receives the request for usage information and, in step 5,provides the usage information to the serving PCRF 102. PCEF 104 knowsthe current real time usage count for the subscriber because PCEF 104enforces policies, including data network usage policies, for thesubscriber. Because the usage information was requested in response tothe PNR message, rather than waiting for the termination of the datasession, PCEF 104 can provide the current usage information, even whilethe subscriber is participating in one or more data sessions.

In step 6, PCRF 102 provides the real time data network usageinformation to SPR 100 via a profile-update request (PUR) message. SPR100 receives the PUR message and, in step 7, provides the real timeusage information to IT system 108. The following illustrated exemplaryfields may be included in a PUR message:

 < Profile-Update-Request > ::=    < Diameter Header: 307, REQ, PXY,16777217 >             < Session-Id >             {Vendor-Specific-Application-Id }             { Auth-Session-State }            { Origin-Host }             { Origin-Realm }             [Destination-Host ]             { Destination-Realm }             *[Supported-Features ]             { User-Identity }             [Wildcarded-Public-Identity ]             [ Wildcarded-IMPU ]            [ User-Name ]             *{ Data-Reference }             {User-Data }             *[ AVP ]             *[ Proxy-Info ]            *[ Route-Record ]In the above listed example, the PUR message includes a user data AVPvalue. The user data AVP value may be used to carry the current datanetwork usage information for the subscriber. However, the subjectmatter described herein is not limited to using a PUR message tocommunicate the current data network usage information from the PCRF tothe SPR. As stated above, any proprietary or non-proprietary message forcarrying this information may be used without departing from the scopeof the subject matter described herein.

In step 8, IT system 108 provides the real time data network usageinformation to subscriber 106. Thus, using the steps illustrated in FIG.2, real time subscriber data network usage information can be providedin response to a request from the subscriber, even while the subscriberis participating in a data session by triggering the SPR to obtainupdated data network usage information in real time.

The subject matter described herein is not limited to providing orobtaining real time data network usage information in response to arequest from the subscriber. In an alternate scenario, the data ormobile network operator may obtain data network usage information in thereal time for the subscriber using the steps illustrated in FIG. 2. Onereason that the network operator may desire to obtain this informationin real time is so that the network operator can take action if thesubscriber is at or near a threshold while the subscriber isparticipating in one or more data network sessions. For example, thenetwork operator may desire to send the subscriber a message where thesubscriber can purchase additional data network capacity if thesubscriber's allocation of data network capacity is about to beexceeded. In another example, the data network operator may simplynotify the subscriber, while the subscriber is participating in one ormore data network sessions, that the subscriber's data network capacityallocation is about to be exceeded.

FIG. 3 is a block diagram illustrating an exemplary architecture for ITsystem 108 for providing real time data network usage information usingan SPR according to an embodiment of the subject matter describedherein. Referring to FIG. 3, IT system 108 includes a subscriberinterface 300 for interfacing with subscribers and an SPR interface 302for interfacing with an SPR. Subscriber interface 300 may be anysuitable interface, such as a hypertext transfer protocol (HTTP)interface for web communications with the subscriber or an interactivevoice response (IVR) interface if the subscriber contacts IT system 108via a telephone call. In another example, subscriber interface 300 maybe an SMS interface for communicating with the subscriber via SMS. SPRinterface 302 may be any suitable interface through which IT system 108can effect the data change in SPR 100 that triggers SPR 100 to obtainupdated data network usage information for a subscriber. For example,SPR interface 302 may be a database related interface where IT system108 can effect subscriber data changes by writing data to subscriberprofiles stored in the subscriber profile data repository maintained bySPR 100. The components in IT system 108 may be implemented or executedby one or more processors 304.

FIG. 4 is a block diagram illustrating an exemplary architecture for SPR100 for providing real time data network usage information according toan embodiment of the subject matter described herein. Referring to FIG.4, SPR 100 includes an IT system interface 400 for interacting with ITsystem 108. IT system interface 400 may receive commands from IT system108 to effect data changes for subscriber profiles stored in subscriberprofile data repository 402. Subscriber profile repository 402 may storeprofiles for each subscriber. Profile 404 for subscriber A is shown asan example. In the illustrated example, profile 404 includes the datanetwork allowance for the subscriber (5 GB), the data network usage forthe subscriber (3.5 GB). SPR 100 may maintain a list of systems that areinterested in being notified of the data change. When the user sessionfirst started, the serving PCRF retrieves the subscriber profile fromthe SPR and at that time ‘subscribed’ to the change notification. TheSPR, upon data change, sends notifications to systems that hadsubscribed previously. In this example, the serving PCRF is PCRF1, whichsubscribes to receive data change notifications for the subscriber.

As stated above, without some triggering mechanism for updating the datanetwork usage information maintained by SPR 100 more frequently than atsession terminations, the usage information stored by SPR 100 may not bereflective of real time data network usage by a subscriber. Oneexemplary triggering mechanism for triggering updates to the subscriberprofile information may be provided by subscriber profile manager 405.Subscriber profile manager 405 may detect changes in subscriber profiledata, for example, when such changes are written to a subscriber profileby IT system 108. When such a change occurs, subscriber profile manager405 may generate the PNR message referenced above for notifying theserving PCRF of the change in subscriber profile data. The PNR messagemay carry information PCRF 102 recognizes as a request for updatesubscriber data usage information.

Although the PNR message provides a convenient existing mechanism forobtaining updated subscriber data network usage information, the subjectmatter described herein is not limited to using the PNR message toobtain this information. In an alternate implementation, a proprietaryor other type of message may be sent that the PCRF recognizes as arequest for updated network information and that triggers the PCRF toobtain this information.

SPR 100 also includes PCRF interface 406 for communicating with PCRF102. PCRF interface 406 transmits the request for updated data networkusage information to PCRF 102, communicates policy-related subscriberinformation to PCRF 102, receives updated data network usage informationfrom PCRF 102, and stores the information in subscriber profile datarepository 402. The components illustrated in FIG. 4 may be executed orimplemented by one or more processors 408.

FIG. 5 is a block diagram illustrating an exemplary architecture forPCRF 102 for providing real time data network usage information using anSPR according to an embodiment of the subject matter described herein.Referring to FIG. 5, PCRF 102 includes an SPR interface 500 forcommunicating with an SPR 100. SPR interface 500 may receivenotifications of data changes from SPR 100 and provide thosenotifications to policy engine 502. Policy engine 502 processes receivedmessages and determines the appropriate action. Policy engine 502 mayalso maintain serving PCEF information 504 for a subscriber. PCRF 102also includes a PCEF interface 506 for communicating with PCEFs 104.PCEF interface 506 may send the request for real time data network usageinformation to PCEF 104 that is serving a subscriber. One or moreprocessors 508 may implement or execute the components of PCRF 102.

FIG. 6 is a block diagram illustrating exemplary components of PCEF 104for providing real time data network usage information using and SPRaccording to an embodiment of the subject matter described herein.Referring to FIG. 6, PCEF 104 includes a PCRF interface 600 forreceiving policies and other messages from PCRF 102. PCEF 104 alsoincludes a policy enforcement engine 602 for enforcing installedpolicies 604 received from PCRF 102. Policy enforcement engine 602 mayalso implement usage counters 606 on a per subscriber basis. Usagecounter 606 maintains a current count of data network usage by eachsubscriber for which a policy is installed. PCEF 104 may include asubscriber data interface 608 for sending data to and from a subscriberover a data network connection. One or more processors 610 may implementor execute the components of PCEF 104.

FIG. 7 is a flow chart illustrating exemplary steps performed by ITsystem 108 in providing real time data network usage information for asubscriber according to an embodiment of the subject matter describedherein. Referring to FIG. 7, in step 700, a request for real time datanetwork usage information for a subscriber is received. For example, ITsystem 108 may receive an SMS message, an e-mail, or a telephone callfrom a subscriber 106 requesting real time data network usageinformation for the subscriber. The request may be received while one ormore data sessions involving the subscriber are still in progress.Alternatively, the request may originate from the mobile networkoperator.

In step 702, in response to the request, IT system 108 triggers SPR 100to update data network usage information for the subscriber. Forexample, as described above, IT system 108 may set a flag in thesubscriber's profile maintained by SPR 100, where the setting of theflag triggers SPR 100 to send a data change notification that will beinterpreted by the PCRF as a request usage information for thesubscriber. In step 704, the IT system 108 receives real time datanetwork usage information for the subscriber. For example, IT system 108may receive a message from SPR 100 including real time data networkusage information for the subscriber or read from the subscriber profilein the SPR and detect the data change.

FIG. 8 is a flow chart illustrating exemplary overall steps performed bySPR 100 in providing real time data network usage information regardinga subscriber. Referring to FIG. 8, in step 800, SPR 100 receives a datachange request for the subscriber. The data change request may be themessage from the IT system 108 for setting a flag in the subscriber'sprofile. The data change request may trigger the SPR to notify theserving PCRF of the change in data for the subscriber. Accordingly, instep 802, SPR 100 identifies the PCRF serving the subscriber. Step 802may be performed by analyzing its own state data to determine any PCRFsthat are subscribed to receive data change notifications for thesubscriber. In step 804, SPR 100 sends a PNR to the serving PCRF. ThePNR may contain a parameter recognized by the PCRF as a request forusage information. In step 806, the SPR receives a PUR containing usageinformation for the subscriber. In step 808, SPR 100 provides the usageinformation to the IT system.

FIG. 9 is a flow chart illustrating exemplary steps performed by PCRF102 in providing real time data network usage information regarding asubscriber. Referring to FIG. 9, in step 900, PCRF 102 receives a PNRfrom the SPR. In step 902, PCRF 102 identifies the PNR as a request forreal time data network usage information for a subscriber. In step 904,PCRF 102 identifies the serving PCEF(s). PCRF 102 may store informationconcerning the serving PCEF(s) because PCRF 102 is the node thatinstalled the policy for the subscriber on the PCEF(s). In step 906,PCRF 102 sends a request for real time data network usage information tothe serving PCEF(s). In step 908, PCRF 102 receives real time datanetwork usage information from the serving PCEF(s) 104, and in step 910provides SPR 100 with an indication of the real time usage informationvia a PUR message. If multiple PCEFs are serving a subscriber, PCRF 102may query each of the PCEFs for the current byte count used by eachsession involving the subscriber and total the byte counts from all ofthe serving PCEFs. The indication of the real time network usageinformation provided in the PUR message may represent the total bytecount for all of the user's current data network sessions. Even in thecase of a single PCEF serving the subscriber, if the PCEF is onlyallocated a portion of the subscriber's data network usage quota, e.g.,a 100 MB chunk of a 1 GB allocation, the PCRF may total the subscriber'susage of the current chunk with usage from all previously allocatedchunks and provide the total to the SPR.

FIG. 10 illustrates exemplary steps performed by PCEF 104 in providingreal time data network usage information regarding a subscriberaccording to an embodiment of the subject matter described herein. Thesteps illustrated in FIG. 10 may be performed by each of a plurality ofPCEFs that are serving a subscriber at a given time. Referring to FIG.10, in step 1000, PCEF 104 receives a request for real time usageinformation for a subscriber. The request may be received while one ormore data network sessions concerning the subscriber are in progress.The request may originate from the serving PCRF 102. In step 1002, thePCEF 104 reads a data network usage counter for the subscriber. The PCEFmay maintain such counters because the PCEF is required, as part of itspolicy enforcement function, to maintain such counters. In step 1004,the PCEF provides real time data network usage information regarding thesubscriber to PCRF 102. The real time data network usage information maybe the current amount of data bytes used by the subscriber while one ormore data network sessions involving the subscriber are in progress.

Thus, by triggering updates of data network usage information maintainedin the SPR, the subject matter described herein is capable of providingreal time data network usage information for a subscriber. The subjectmatter described herein uses a modification of an existing mechanism toeffect the updating of the data network usage information. It will beunderstood that various details of the presently disclosed subjectmatter may be changed without departing from the scope of the presentlydisclosed subject matter. Furthermore, the foregoing description is forthe purpose of illustration only, and not for the purpose of limitation.

What is claimed is:
 1. A method for providing real time data networkusage information for a subscriber utilizing a subscription profilerepository (SPR), the method comprising: at the SPR: receiving, from apolicy and charging rules function (PCRF), a message subscribing to datachange notifications for a subscriber; receiving, from a network deviceseparate from the PCRF, a data change request for the subscriber;transmitting from the SPR to the PCRF as a consequence of the PCRFsubscribing to the data change notifications for the subscriber and thedata change request, a push notification request (PNR) for real timedata network usage information for the subscriber; and receiving, fromthe PCRF, an indication of the real time data network usage for thesubscriber.
 2. The method of claim 1 comprising, at the PCRF and inresponse to the PNR, requesting real time data network usage informationfor the subscriber from at least one policy and charging enforcementfunction (PCEF) and receiving the real time data network usageinformation from the at least one PCEF.
 3. The method of claim 2 whereinreceiving the real time data network usage information from the at leastone PCEF includes receiving a byte count from the PCEF reflecting datanetwork usage information for the subscriber while the subscriber isparticipating in one or more data network sessions.
 4. The method ofclaim 1 wherein the network device comprises an information technology(IT) system of a data network operator.
 5. The method of claim 4 whereinthe IT system generates the data change request for the subscriber inresponse to a request for real time network usage informationoriginating from a subscriber device and carried in one of a phone call,a text message, or an e-mail from the subscriber device.
 6. The methodof claim 1 comprising effecting a data change for the subscriber in theSPR in response to the data change request by setting a flag in aprofile for the subscriber maintained by the SPR.
 7. The method of claim1 wherein receiving, from the PCRF, real time data network usageinformation for the subscriber includes receiving the real time datanetwork usage information in a profile update request (PUR) message. 8.The method of claim 1 comprising providing the real time data networkusage information from the SPR to the network device.
 9. The method ofclaim 1 wherein the real time data usage information comprises long termevolution (LTE) data network usage information.
 10. A system forproviding real time data network usage information for a subscriberutilizing a subscription profile repository (SPR), the systemcomprising: an SPR comprising: a processor; a first interface forreceiving, from a policy and charging rules function (PCRF), a messagesubscribing to data change notifications for a subscriber; a secondinterface for receiving, from a network device separate from the PCRF, adata change request for the subscriber; wherein the first interfacetransmits from the SPR to the PCRF as a consequence of the PCRFsubscribing to the data change notifications for the subscriber and thedata change request, a push notification request (PNR) for real timedata network usage information for the subscriber; and wherein thesecond interface receives, from the PCRF, an indication of the real timedata network usage information.
 11. The system of claim 10 wherein thePCRF, in response to the PNR, requests real time data network usageinformation for the subscriber from at least one policy and chargingenforcement function (PCEF) and receives the real time data networkusage information from the at least one PCEF.
 12. The system of claim 11wherein the PCRF is configured to receive a byte count from the at leastone PCEF reflecting data network usage information for the subscriberand provide the indication of the real time data network usageinformation to the SPR while the subscriber is participating in one ormore data network sessions without waiting for the termination of theone or more data network sessions.
 13. The system of claim 10 whereinthe network device comprises an information technology (IT) system of adata network operator.
 14. The system of claim 10 wherein the IT systemgenerates the data change request for the subscriber in response to arequest for real time data network usage information communicated from asubscriber device via one of a phone call, a text message, or an e-mail.15. The system of claim 10 wherein the IT system is configured to effectthe data change for the subscriber in the SPR by setting a flag in aprofile for the subscriber maintained by the SPR.
 16. The system ofclaim 10 wherein the SPR is configured to receive the real time datanetwork usage information from the PCRF via a profile update request(PUR) message.
 17. The system of claim 10 wherein the network devicecomprises an information technology (IT) system and wherein the SPR isconfigured to provide the real time data network usage information tothe subscriber by way of the IT system.
 18. A non-transitory computerreadable medium having stored thereon executable instructions that whenexecuted by the processor of a computer control the computer to performsteps comprising: at the SPR: receiving, from a policy and chargingrules function (PCRF), a message subscribing to data changenotifications for a subscriber; receiving, from a network deviceseparate from the PCRF, a data change request for the subscriber;transmitting from the SPR to the PCRF as a consequence of the PCRFsubscribing to the data change notifications for the subscriber and thedata change request, a push notification request (PNR) for real timedata network usage information for the subscriber; and receiving, fromthe PCRF, an indication of the real time data network usage for thesubscriber.